Both of the Kleartxt samples were built with CW Pro 5. The PGPuam Sample was built with CW Pro 4. You should go to <http://www.vmeng.com/vinnie/Papers/pgpuam.html> to get the latest version of the PGP UAM. You will also need an ASIP 6.1 (or later) server and a 3.8.1 (or later) client.
What doesn't work yet
Server side
Setting the Message Integrity Code key
Change Password
Client side
asynchronous callbacks
the SetMicKey() call is stubbed out for now.
There is a problem with letting the AppleShare Client run the password dialog, for now, you need to supply your own password dialog. This problem should be fixed in a future Client. btw this means that the Kleartxt sample won't work correctly, the passwords won't match.
The UAM API and Carbon:
The client side UAM API is Carbon compliant. Under Carbon the callbacks go back to being function pointers instead of UPPs. There may be a new format for UAMs under carbon, ie we may not be doing code resources, but we will still have a single entrypoint. If you are planning on carbon compliance for your client side UAM, start by making a PPC resource with the routine descriptor at the start of the resource pointing to the PPC entry point.